Method and apparatus for performing an authentication after cipher operation in a network processor

ABSTRACT

A method and apparatus is described for processing of network data packets by a network processor having cipher processing cores and authentication processing cores which operate on data within the network data packets, in order to provide a one-pass ciphering and authentication processing of the network data packets.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/455,038, filed on May 27, 2009, which issued as U.S. Pat. No.8,041,945, and entitled, “METHOD AND APPARATUS FOR SCHEDULING THEPROCESSING OF COMMANDS FOR EXECUTION BY CRYPTOGRAPHIC ALGORITHM CORES INA PROGRAMMABLE NETWORK PROCESSOR,” which is a continuation of U.S.patent application Ser. No. 10/741,676, filed on Dec. 19, 2003, whichissued as U.S. Pat. No. 7,543,142, and entitled, “METHOD AND APPARATUSFOR SCHEDULING THE PROCESSING OF COMMANDS FOR EXECUTION BY CRYPTOGRAPHICALGORITHM CORES IN A PROGRAMMABLE NETWORK PROCESSOR,” is herebyincorporated by reference in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH

Not Applicable

FIELD OF THE INVENTION

This invention relates generally to network processors and moreparticularly to a method and apparatus for scheduling cipher processingand authentication processing in a programmable network processor.

BACKGROUND OF THE INVENTION

As is known in the art, there is a trend to provide network processorsthat perform cryptographic processing of network packets. To facilitatethe cryptographic processing, the network processors includecryptographic acceleration units (also referred to as “crypto units”).The crypto units accelerate the cryptographic processing of packet datato support cryptographic processing at network line rate. One example ofa network processor including such a crypto unit is the INTEL® IXP2850network processor manufactured by Intel Corporation.

Two types of cryptographic processing that are commonly performed onnetwork packets are authentication processing (or more simplyauthentication) and ciphering processing (or more simply ciphering).Authentication is the process of creating a digest of the packet calleda MAC (message authentication code), which is sent along with thepacket, and which allows the receiver to verify that the packet wasindeed sent by the sender (rather than by some third party) and was notmodified in transit. Ciphering is the process of encrypting ordecrypting the packet, so that only the intended receiver, with thecorrect cryptographic key, can decrypt the packet and read its contents.Commonly used security protocols perform both ciphering andauthentication on each network packet.

Known cipher algorithms include, but are not limited to, 3DES, AES, andRC4 cipher algorithms. The 3DES and AES algorithms are block cipheralgorithms, which means that they process data in discrete blocks. Theprocessing block size of the 3DES algorithm is 8 bytes, the processingblock size of the AES algorithm is 16 bytes, and the RC4 algorithm is astream cipher and processes data one byte at a time. These are but someof many cipher algorithms, and have processing block sizesrepresentative of other cipher algorithms.

Known authentication algorithms include, but are not limited to, MD5,SHA1, and AES-XCBC-MAC authentication algorithms. All of these areblock-oriented algorithms. The processing block size of the MD5 and SHA1algorithms is 64 bytes, while the AES-XCBC-MAC algorithm uses a blocksize of 16 bytes. These are but some of many authentication algorithms,and have processing block sizes representative of other authenticationalgorithms. It should be appreciated that the length of a network datapacket is not required to be a multiple of the block size of aparticular cipher or authentication algorithm.

Known security protocols such as IPSEC provide part of the data in anetwork packet that is subject to ciphering and authentication, whileanother part of the data is subject only to authentication. The datathat is subject only to authentication generally appears at thebeginning of the packet. Other security protocols have a similarrequirement that part of the data in a network packet is subject tociphering and authentication, while another part of the data is subjectonly to authentication.

It should be appreciated that different security protocols can havedifferent size headers associated with a network packet and that theamount of data subject to authentication only is not necessarily amultiple of the block size of the cipher and/or authenticationalgorithm.

Network packet data subject to ciphering and authentication can have twovarieties. In a first variety, as discussed more fully below, incomingunencrypted data subject to ciphering and authentication (to beencrypted) can be ciphered and then sequentially processed by theauthentication core. In a second variety, incoming encrypted datasubject to ciphering and authentication (to be decrypted) can beprocessed by both the authentication and cipher cores substantially inparallel. Whether the ciphering and the authentication operations areperformed sequentially or in parallel can depend not only on whetherpackets are to be encrypted or decrypted, but can also depend on thespecific security protocol used, for example IPSec.

Once ciphered with the cipher core, data that is ciphered and not yetprocessed by the authentication core can be referred to asciphered-network-packet data subject to authentication. Therefore, for anetwork data packet associated with a security protocol, different typesof data exist, including network packet data subject to authenticationand ciphering, network packet data subject only to authentication, andciphered-network-packet data subject to authentication.

In order to provide both cipher processing and authenticationprocessing, some prior art techniques employ a two-pass approach. In thetwo-pass approach, a network packet is processed in a first pass withcipher processing of network packet data subject to ciphering andauthentication. The network packet is then processed in a second passwith authentication processing of the resulting ciphered-network-packetdata subject to authentication along with network packet data subjectonly to authentication. As networks become faster, the two-pass approachtends to limit throughput of network packets. In order to perform bothciphering and authentication at a high data rate, it would be desirableto perform both operations in one pass.

Therefore, it would be desirable to overcome the aforesaid and otherdisadvantages, and to provide a method and apparatus that can process anetwork packet data in a security protocol having ciphering andauthentication, at full network line speed. It would be furtherdesirable to provide the method and apparatus that is readily adaptableto processing with any cipher algorithm and any authenticationalgorithm.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing features of the invention, as well as the invention itselfmay be more fully understood from the following detailed description ofthe drawings, in which:

FIG. 1 is a block diagram of an exemplary embodiment of a networkprocessor having an authentication buffer;

FIG. 2 is a block diagram of an exemplary authentication buffer in afirst state;

FIG. 2A is a block diagram of the exemplary authentication buffer ofFIG. 2 in a second state;

FIG. 2B is a block diagram of the exemplary authentication buffer ofFIG. 2 in a third state; and

FIG. 3 is a flow chart showing a process of using an authenticationbuffer.

DETAILED DESCRIPTION OF THE INVENTION

Before describing the method and apparatus for performing authenticationafter cipher, some introductory concepts and terminology are explained.As used herein, the term “data” refers to any portion of a networkpacket, including but not limited to, header information, source addressinformation, destination address information, and user data. The networkpacket can be in any format, including, but not limited to IP, TCP/IP,and Ethernet.

Also, as used herein, the terms “network packet data subject tociphering and authentication,” “network packet data subject only toauthentication,” and “ciphered-network-packet data subject toauthentication,” are distinct types of data associated with a securityprotocol and with a network packet as described by the terms and asfurther described below. It will become apparent from discussions belowthat the network packet data subject to ciphering and authentication canhave two varieties, a first variety in which the ciphering and theauthentication are performed sequentially upon received unencryptednetwork packet data, and a second variety in which the ciphering and theauthentication are performed substantially in parallel upon receivedencrypted network packet data.

As used herein, “ciphering” refers both to encrypting and decryptingdata associated with a network packet.

Referring now to FIG. 1, an exemplary network processor 10 includes acryptographic unit 16 having a scheduler 18 adapted to receive networkpackets 17. The scheduler 18 is coupled to a cipher core group 24 and toan authentication buffer group 28. As described above, securityprotocols such as IPSEC require that part of the data in a networkpacket is subject to authentication and ciphering, and part of the datais subject only to authentication. Thus, the scheduler 18 directsportions of the network packets along selected paths 20, 22. Thescheduler 18 directs the first variety of network packet data subject tociphering and authentication, for which ciphering and authentication areto be performed sequentially as described above, along the path 22 to aselected cipher core within the cipher core group 24. The scheduler 18also directs the second variety of network packet data subject tociphering and authentication, for which ciphering and authentication areto be performed substantially in parallel as described above, along thepath 22 to the cipher core group 24 and also along a path 20 to aselected authentication buffer within an authentication buffer group 28.The scheduler 18 further directs network packet data subject only toauthentication (no ciphering) along the path 20 to the selectedauthentication buffer within an authentication buffer group 28. It willbe understood that the network packet data subject only toauthentication is also directed elsewhere in the network processor 10,though not explicitly shown.

In the exemplary network processor 10 of FIG. 1, the cipher core group24 include two 3DES cipher cores 24 a, 24 b, respectively, using a 3DESalgorithm, one AES cipher core 24 c using an AES algorithm, and one RC4cipher core 24 d using an RC4 algorithm. As described above, theprocessing block size of the 3DES algorithm is 8 bytes, the processingblock size of the AES algorithm is 16 bytes, and the RC4 algorithmperforms a stream cipher, which processes data one byte at a time.

The cipher core group 24 provides ciphered-network-packet data subjectto authentication along a path 26 to the selected authentication bufferwith the authentication buffer group 28. The cipher core group 24 alsotransmits ciphered network packet data out of the cryptographic unit 16along path 36.

It will therefore be understood that the selected authentication bufferstores “authentication data” including at least one ofciphered-network-packet data subject to authentication, network packetdata subject only to authentication, and network packet data subject tociphering and authentication.

Blocks of the authentication data are provided along a path 30 from theauthentication buffer group 28 to a selected authentication core withinan authentication core group 32. The authentication core group 32includes two MD5 cores 32 a, 32 b using an MD5 algorithm, two SHA1 cores32 c, 32 c using an SHA1 algorithm, and one AES-XCBC-MAC core 32 e usingan AES-XCBC-MAC algorithm. As described above, the processing block sizeof the MD5 and SHA1 algorithms is 64 bytes, while the AES-XCBC-MACalgorithm uses a block size of 16 bytes. Message authentication codes(MACs) 34 that result from the authentication operation performed on apacket are provided by the authentication core group 32.

The authentication buffer, e.g., authentication buffer 28 a, provides ameans of operating with the cipher cores 24 a-24 d and withauthentication cores 32 a-32 f having different processing block sizes,while maintaining a consistent throughput at network line speed. Thefunction of the authentication buffers 28 a-28 f will become apparent inconjunction with figures below.

A processor 12 provides commands along a path 14, which control thescheduler 18 to provide the portions of the network packets whichrequire ciphering and authentication and the portions of the networkpackets requiring only authentication along the paths 22, 20,respectively, as described above. The processor 12 also providescommands to select a cipher core 24 a-24 d from among the cipher coregroup 24, an authentication buffer 28 a-28 f from among theauthentication buffer group 28, and an authentication core 32 a-32 ffrom among the authentication core group 32.

Having more than one authentication buffer in the authentication buffergroup 28 allows parallel operations to be performed upon multiplenetwork packets at the same time, therefore tending to increasethroughput speed.

The authentication buffers 28 a-28 e decouple and speed match theoperation of the cipher cores 24 a-24 d and the operation of theauthentication cores 32 a-32 e, which can operate at different datarates and on blocks of data having different sizes. Each authenticationbuffer 28 a-28 f is sized to hold at least a largest block of dataassociated with any of the supported authentication algorithms, plus alargest block of data associated with any of the supported cipheralgorithms. For the exemplary embodiment shown in FIG. 1, MD5 and SHA1have a block size of 64 bytes and AES-XCBC-MAC has a block size of 16bytes, so at least one of the authentication buffers 28 a-28 f must holdat least 64 bytes of network packet data subject only to authentication(i.e., from path 20) plus at least 16 bytes of ciphered-network-packetdata subject to authentication (i.e., from path 26). Therefore, for theexemplary embodiment shown in FIG. 1, each of the authentication buffers28 a-28 f includes at least eighty bytes. However, in other embodiments,one or more of the authentication buffers 28 a-28 f can have more thanor fewer than eighty bytes, in accordance with supported cipher andauthentication algorithms.

In order to support the ciphering network packets, the exemplarycryptographic unit 16 has six processing “contexts” and sixcorresponding authentication buffers 28 a-28 f, which are each used toprocess one packet at a time. A processing context corresponds to avariety of information, including a cipher key and intermediateciphering/authentication results associated with the processing of onepacket. Multiple processing contexts and a corresponding plurality ofauthentication buffers allow any latency generated by loading ofcryptographic key material and packet data to be hidden. In essence, thecryptographic unit 16 is pipelined, allowing the loading of data and keymaterial associated with some of the contexts concurrently withprocessing of data associated with other contexts. This allows thecryptographic unit 16 to achieve a high throughput.

It should be understood that although in the exemplary embodiment ofFIG. 1, the cipher core group 24 is comprised of four cipher cores 24a-24 d, in other embodiments the cipher core group 24 can have more thatfour or fewer than four cipher cores, and can also have different ciphercores, operating with different cipher algorithms than those shown.Also, it should be understood that although in the exemplary embodimentof FIG. 1, the authentication core group 32 is comprised of five cores32 a-32 e, in other embodiments the authentication core group 32 canhave more than five or fewer than five authentication cores, and canalso have also different authentication cores, operating with differentauthentication algorithms than those shown. Also, in other embodiments,the network processor 10 can have more than one cryptographic unit 16,and each of the cryptographic units can be the same or different, forexample supporting the same or different cipher and/or authenticationalgorithms. In one exemplary embodiment, the network processor 10 hastwo cryptographic units 16, each as shown. The maximum number ofcryptographic units 16, the maximum number of cores, and the maximumnumber of authentication buffers which can be included in a in thenetwork processor 10 is limited only by practical manufacturingconsiderations, e.g., maximum practical silicon die area.

While six authentication buffers are shown, it should also beappreciated that more than six or fewer than six authentication bufferscan be used. The number of authentication buffers to use is selected inaccordance with a desired number or processing contexts resulting in acorresponding number of authentication buffers being loaded and/orprocessed in parallel.

Referring now to FIGS. 2-2B, a table 70 represents eighty byte locationscorresponding to one of the authentication buffers 28 a-28 f of FIG. 1,and will be referred to herein as an authentication buffer 70.

The authentication buffer 70 is arranged as a circularfirst-in-first-out (FIFO) memory. The FIFO structure allows the blocksize of the data being written to the buffer to be different from theblock size of the data being read from the buffer. This allows a writeoperation to provide more data than is required by an authenticationcore, e.g., authentication core 32 a of FIG. 1, while the authenticationcore reads the data block. A start of data pointer 72, corresponding toa logical start of the authentication buffer 70, is associated with astart of data within the authentication buffer 70. An end of datapointer 74, corresponding to a logical end of the authentication buffer70, is associated with an end of data within the authentication buffer70. The start of data pointer 72 points to a start of the next datablock to be processed by the authentication core (e.g., authenticationcore 32 a, FIG. 1), and the end of data pointer 74 points to a next bytelocation to which data will be written.

When enough data has accumulated in the authentication buffer 70 to filla data block, required by an authentication algorithm associated withthe authentication core, then the block of data is read from theauthentication buffer 70 and sent to an authentication core, e.g.,authentication core 32 a, of FIG. 1, for authentication processing. Asufficient block of data can be identified by sufficient separationbetween the start of data pointer 72 and the end of data pointer 74. Itshould be recognized that the block of data need not actually be removedfrom the authentication buffer 70. Rather, merely moving the start ofdata pointer 72 effectively removes the data block from furtherprocessing.

Further operation of the authentication buffer 70 is described in termsof an example. In operation, initially the start of data pointer 72 andthe end of data pointer 74 each point to the first physical byte of theauthentication buffer 70 (byte 0). In one example, 12 bytes of networkpacket data subject only to authentication are loaded into theauthentication buffer 70 and the end of data pointer 74 is moved to byte12 accordingly. In FIG. 2, crosshatched boxes represent bytes into whichdata has been loaded, but not yet processed by an authentication core.

Referring now to FIG. 2A, continuing with the above example, another 64bytes of data (four 16-byte blocks) are written to the authenticationbuffer 70. The authentication buffer 70 now contains 76 bytes of data,enough data for an authentication algorithm to start processing. The endof data pointer 74 is moved accordingly to the next byte to which datacan be written, which is here byte 76.

When the authentication buffer 70 contains sufficient data to beginauthentication processing, a block of data is processed, which is here64 bytes. The authentication core processes 64 bytes of data starting atthe start of data pointer 72. In this example, therefore, theauthentication core processes bytes 0 through 63.

When the authentication core has processed the data, the start of datapointer 72 is advanced to point to byte 64 and the end of data pointer74 remains at byte 76.

Referring now to FIG. 2B, when another 16-byte block of data arrives,for example from the cipher core 28 a of FIG. 1 asciphered-network-packet data subject to authentication, four bytes arewritten at the end of the authentication buffer 70 and the remaining 12bytes are written starting at the (physical) beginning of theauthentication buffer 70. Also, the end of data pointer 74 is movedaccordingly to byte 12. When 64 bytes have accumulated in the buffer,the authentication core again processes the block of data. The first 16bytes of that block will be read from physical locations 64-79. Theremaining 48 bytes will be read from physical locations 0-47. Thisprocess continues until the processing of a network data packet iscomplete.

It should be understood that though the authentication buffer 70 canhave a fixed physical size, for example, eighty bytes, by means of thestart of data pointer 72 and the end of data pointer 74, the actualnumber of bytes used in the circular FIFO structure can be changed orprogrammed to have any length of eighty bytes or less. The programmingcan be provided, for example, by the processor 12 of FIG. 1. In otherembodiments, the authentication buffer 70 can include more than eightyor fewer than eighty bytes

In one particular embodiment, the authentication buffer 70 isimplemented as an 80-byte circular FIFO using byte-writeable registerfiles. Register files allow new network packet data to be written intothe authentication buffer 70 byte-by-byte as they arrive without havingto shift the data through an accumulation buffer 70.

Register files, which in one embodiment, are used to implement thecircular FIFO authentication buffer 70, use a smaller amount ofintegrated circuit die area than flip-flop structures. Typically, animplementation using register files is two or three times more die areaefficient than an implementation using flops. As is known, registerfiles are composed of memory cells, decoders, and read/write circuitry.Register files use memory cells, which are approximately one third thesize of flip-flops. In addition, data read from a register file does notneed to be multiplexed between outputs of flip-flops. For registerfiles, multiplexing is performed very efficiently by a register file bitline structure. Therefore, register files require a smaller integratedcircuit die area than flip-flops.

It should be appreciated that the example described in conjunction withFIGS. 2-2B performs both the ciphering operation and the authenticationoperation in one pass, i.e., a network packet is processed once, andtherefore performs the ciphering and authentication processing rapidly.

Referring now to FIG. 3, a process 100 for providing and using acircular FIFO authentication buffer, e.g., authentication buffer 70 ofFIGS. 2-2B, begins at step 102, where an authentication buffer (e.g.,authentication buffer 32 a, FIG. 1) is selected from among a group ofauthentication buffers (e.g., 32, FIG. 1). The selection can be basedupon a variety of criteria, including, but not limited to, selection ofan idle authentication buffer.

At step 104 a start of data pointer and end of data pointer are set topoint to the start of the authentication buffer, as described above inconjunction with FIG. 2.

At step 106, one or more blocks of network packet data are moved to theselected authentication buffer selected at step 102. This data can benetwork packet data subject only to authentication as provided along thepath 20 of FIG. 1, network packet data subject to ciphering andauthentication as provided along the path 20 of FIG. 1,ciphered-network-packet data subject to authentication as provided alongpath 26 of FIG. 1, or padding data required at the end of the packet inorder to make the length of the data processed by the authenticationcore a multiple of the authentication algorithm block size. The order inwhich these different types of data are received is controlled bysoftware running on the processor 12 (FIG. 1). The order depends on theprotocol (e.g., IPSEC or SSL) and on the operation (encryption ordecryption) being performed.

At step 108, an end of data pointer is set to point to a locationimmediately after the end of data within the authentication buffer, tothe next location to which data can be written.

At step 110, a decision is made as to whether there is enough data inthe selected authentication buffer to allow a selected authenticationcore, having a predetermined authentication algorithm associated with apredetermined data block size, to operate on the data within theselected authentication buffer. If there is not enough data, the processreturns to step 106. If enough data has been received the processproceeds to step 112.

At step 112 a data block corresponding in size to the predetermined datablock size is moved to an authentication core (e.g., authentication core32 a, FIG. 1) for authentication processing.

At step 114, the start of data pointer is set in accordance with thedata block being moved to an authentication core at step 112, asdescribed above in conjunction with FIGS. 2-2B

At step 116 a decision is made as to whether the last data has beenreceived from a network data packet. If the last data has been received,the process ends. If the last network data has not yet been received,the process returns to step 106.

Having described preferred embodiments of the invention it will nowbecome apparent to those of ordinary skill in the art that otherembodiments incorporating these concepts may be used. Additionally, thesoftware included as part of the invention may be embodied in a computerprogram product that includes a computer useable medium. For example,such a computer usable medium can include a readable memory device, suchas a hard drive device, a CD-ROM, a DVD-ROM, or a computer diskette,having computer readable program code segments stored thereon. Thecomputer readable medium can also include a communications link, eitheroptical, wired, or wireless, having program code segments carriedthereon as digital or analog signals. Accordingly, it is submitted thatthat the invention should not be limited to the described embodimentsbut rather should be limited only by the spirit and scope of theappended claims. All publications and references cited herein areexpressly incorporated herein by reference in their entirety.

What is claimed is:
 1. A processor, comprising: an authentication bufferconfigured to store data to be authenticated by at least oneauthentication core, each of the at least one authentication core beingconfigured to operate with an authentication algorithm, the data to beauthenticated comprising ciphered-network-packet data subject toauthentication, network packet data subject only to authentication andnot to ciphering, and network packet data subject to ciphering andauthentication; and the at least one authentication core coupled to theauthentication buffer to authenticate the data from the authenticationbuffer, wherein the authentication buffer is configured to decouple andspeed match an operation of the at least one authentication core bybeing configured to hold at least a largest block of data associatedwith any authentication algorithm associated with the at least oneauthentication core.
 2. The processor of claim 1, wherein the networkprocessor further includes at least one cipher core, each of the atleast one cipher core being configured to operate with a cipheralgorithm, wherein the authentication buffer is configured to decoupleand speed match an operation of the at least one authentication core andthe at least one cipher core by being configured to hold at least alargest block of data associated with any authentication algorithmassociated with the at least one authentication core and a largest blockof data associated with any cipher algorithm associated with the atleast one cipher core.
 3. The processor of claim 1, wherein theauthentication core is configured to authenticate the data from theauthentication buffer as blocks of authentication data.
 4. A network,comprising: a processor having: an authentication buffer configured tostore data to be authenticated by at least one authentication core, eachof the at least one authentication core being configured to operate withan authentication algorithm, the data to be authenticated comprisingciphered-network-packet data subject to authentication, network packetdata subject only to authentication and not to ciphering, and networkpacket data subject to ciphering and authentication; and the at leastone authentication core coupled to the authentication buffer toauthenticate the data from the authentication buffer, wherein theauthentication buffer is configured to decouple and speed match anoperation of the at least one authentication core by being configured tohold at least a largest block of data associated with any authenticationalgorithm associated with the at least one authentication core.
 5. Thenetwork of claim 4, wherein the authentication buffer comprises acircular first-in-first-out (FIFO) arrangement, and wherein the circularFIFO arrangement comprises a moveable start of data pointer and amoveable end of data pointer.
 6. The network of claim 4, wherein theprocessor further includes at least one cipher core, each of the atleast one cipher core being configured to operate with a cipheralgorithm, wherein the authentication buffer is configured to decoupleand speed match an operation of the at least one authentication core andthe at least one cipher core by being configured to hold at least alargest block of data associated with any authentication algorithmassociated with the at least one authentication core and a largest blockof data associated with any cipher algorithm associated with the atleast one cipher core.
 7. The network of claim 4, wherein theauthentication core is configured to authenticate the data from theauthentication buffer as blocks of authentication data.
 8. A method ofauthenticating network packet data, comprising: moving to anauthentication buffer data to be authenticated by at least oneauthentication core, each of the at least one authentication core beingconfigured to operate with an authentication algorithm, the data forauthentication comprising ciphered-network-packet data subject toauthentication, network packet data subject only to authentication andnot to ciphering, and network packet data subject to ciphering andauthentication; and moving to the authentication core a block of datafrom the authentication buffer, wherein the authentication buffer isconfigured to decouple and speed match an operation of the at least oneauthentication core by being configured to hold at least a largest blockof data associated with any authentication algorithm associated with theat least one authentication core.
 9. The method of claim 8, wherein themoving to an authentication buffer data to be authenticated comprisesselecting the authentication buffer from among a plurality ofauthentication buffers.
 10. The method of claim 8, further comprising:setting a start of data pointer and an end of data pointer to respectiveinitial locations; setting the end of data pointer in accordance withthe moving the data to be authenticated to the authentication buffer;and setting the start of data pointer in accordance with the moving tothe authentication core the block of data from the authenticationbuffer.
 11. The method of claim 8, wherein the authentication buffercomprises a circular first-in-first-out (FIFO) arrangement and thecircular first-in-first-out (FIFO) arrangement includes a moveable startof data pointer and a moveable end of data pointer.
 12. The method ofclaim 8, further including: providing a cipher core configured tooperate with a cipher algorithm; providing the authentication coreconfigured to operate with an authentication algorithm, and sizing theauthentication buffer in accordance with a data block size associatedwith the cipher algorithm and a data block size associated with theauthentication algorithm.